Migrate the build system to Meson/meson-python#301
Migrate the build system to Meson/meson-python#301agriyakhetarpal wants to merge 47 commits intomainfrom
Conversation
|
Woohoo 😄 I planned my day for another FOSS project and I won't be able to check it today but I'll try to chime in in the next couple days. |
|
Absolutely, of course! |
Co-Authored-By: Ülgen Sarıkavak <[email protected]>
agriyakhetarpal
force-pushed
the
meson-python!
branch
from
bdaeb0a to
8c4ae9b
Compare
|
Note to self: see if we can implement expanding |
|
(Last three commits were authored with AI assistance, BTW) |
|
Okay, at this point we're at the stage where the editable installations and the regular installation tests work all fine, just that we're stuck because of the mixed layout of the Hugo executable landing in a platdir and |
| - name: Resolve Windows Meson cross file | ||
| id: meson-cross-file | ||
| shell: pwsh | ||
| run: | | ||
| $crossFile = (Resolve-Path (Join-Path $env:GITHUB_WORKSPACE 'meson_cross_files/windows-arm64.ini')).Path -replace '\\', '/' | ||
| "path=$crossFile" >> $env:GITHUB_OUTPUT | ||
|
|
There was a problem hiding this comment.
We can remove this mess once pypa/cibuildwheel#2827 is part of a release 😄
2 participants
Closes #62
Closes #188
See also #6; this adds testing for the editable installation. Might be overkill, but it was a good way to learn what Meson was doing.
cc: @ulgens; if you'd like to take a look! Sorry if you wanted to take this – I woke up super enthusiastic today and decided today's the day to tackle it once and for all :D